The switch has an SNMP agent that supports SNMPv1. This allows it to be managed by any SNMP-based application that supports the MIBs supported by the switch. The switch SNMP agent communicates with:
The SNMP-based application must specify the appropriate community name that the switch is configured to support. Real-time trap messages can be configured to be sent to designated trap receivers. All configuration information on the switch has read/write access via SNMP. All status information is also available via SNMP.
Refer to Using the Terminal Interface for details about configuring SNMP and SNMP trap receiver.
Refer to the various SNMP RFCs that are supported because the SNMP
specification is not described in this chapter. MIBs supported by the
switch are shown in Table 13.
Table 13. MIBs Supported by the Switch.
| MIBs Supported |
|---|
| MIB-II (RFC 1213) |
| Definitions of Managed Objects for Bridges (RFC 1493) |
| IEEE 802.3 Ethernet MIB (RFC 1643) |
| RMON MIB (RFC 1757) |
| IBM 8275-416 MIB |
The latest 8275-416 MIBs can be obtained from our Web site at:
http://www.ibm.com/networking/support
| Note: | Exceptions to the 8275-416 support for the MIBs listed in Table 13 are described in the sections that follow in this chapter. |
The following are 8275-416 exceptions to the support of MIB II groups:
The switch automatically collects and provides information for the MIB II groups that it supports. There are no additional configuration parameters to enable or disable this support.
RFC 1493 defines objects for managing MAC bridges based on IEEE 802.1D-1990 standard between local areas network (LAN) segments. The following objects are 8275-416 exceptions to definitions of managed objects for bridges:
RFC 1643 defines objects for managing Ethernet-like objects. The following objects are 8275-416 exceptions to IEEE 802.3 Ethernet MIB.
The switch automatically collects and provides information for the IEEE 802.3 Ethernet MIB groups that it supports. There are no additional configuration parameters to enable or disable this support.
The RMON MIB defines objects that allow a device to act like a network traffic analyzer monitoring flows and gathering data for all traffic on the network with varying degrees of detail. It is recommended that a Remote Monitor application be used to manipulate RMON MIB objects. Unexpected results can occur if an SNMP MIB browser is used to manipulate RMON MIB objects.
| Note: | The switch only supports up to 10 history buckets per history instance. |
Many of the items needed to obtain information from a switch are not available in standard MIBs. A private MIB for the switch (referred to as the IBM 8275-416 Switch Enterprise MIB) was created for these items.
The following objects in the 8275-416 MIB are not supported by this version of code:
Whenever the above objects are accessed, the switch will return an SNMP GetResponse-PDU[2] error-status = no SuchName(2)
When you use SNMP, the interface index (ifIndex) is sometimes used to identify the specific interface being addressed. On the switch, each Ethernet port is an interface and so is the IP agent being used to manage it (which is also referred to as the Management Interface).
The total number of ifIndex values in the switch is the number of installed ports plus 1. The "1" is for the Management Interface. The port ifIndex values for the switch ports start with 1 and increment by 1 for each port physically in the box. Each ifIndex value maps, one for one, with an Ethernet port. Example scenarios:
The management interface will always have an ifIndex of 1000.